home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.7 KB | 40 lines | [TEXT/GEOL] |
- Item 8350823 7-Nov-90 10:33PST
-
- From: V0683 Amoco Tech, Eric Berdahl,VAR
-
- To: CDA0220 DEV Bell Northern Resrch,B Papp,IDV
- MACAPP.TECH$ MacApp Technical
-
- Sub: Re[2]: Sharable 'CODE' segs
-
- Mark,
-
- This is an exciting proposition you've put before us. I, for one, think it
- holds great possibilities. However, I also see alot of pitfalls.
-
- • Since we must still link a program together, we will need linker support for
- the notion of "there will be no reference to the function foo because it will
- be loaded from some memory already set up by an INIT (or whatever)."
- • We should include a great amount of sanity checking. This should include
- stuff like, "I compiled MacApp to .Debug MacII+, the code currently loaded in
- the Sharable Area is .NoDebug Sym. These are incompatible so I must <fill in
- the blank>."
- • NO application code (as opposed to MacApp code) can be put in a MacApp
- "Sharable" segment. The corrolary of this is that all application code must be
- put in non-MacApp segments. Thus, we will have to be careful about our segment
- mappings.
- • We will need to pre-agree on the segment number and offset of each MacApp
- routine or method. Currently, this may be easy or not.
-
- The main impediment I can see at this time is the fact that the linker does
- alot that we will have to override and set to certain constant stuff.
- Nonetheless, the benefits are obvious and sizeable. Perhaps a future version
- of the ROM will even have some MacApp stuff in it, hmmm? Seems like the
- ultimate sharable code to me.
-
- Skating along,
- Eric Berdahl
- Amoco Technology Company
- AppleLink: V0683
-
-